Configuring TLS is essential for server installation in Trilium. This guide details the steps to set up TLS within Trilium itself.
For a more robust solution, consider using TLS termination with a reverse proxy (recommended, e.g., Nginx). You can follow a guide like this for such setups.
You have two options for obtaining a TLS certificate:
config.iniOnce you have your certificate, modify the config.ini file
in the data directory to configure
Trilium to use it:
[Network]
port=8080
# Set to true for TLS/SSL/HTTPS (secure), false for HTTP (insecure).
https=true
# Path to the certificate (run "bash bin/generate-cert.sh" to generate a self-signed certificate).
# Relevant only if https=true
certPath=/[username]/.acme.sh/[hostname]/fullchain.cer
keyPath=/[username]/.acme.sh/[hostname]/example.com.key
You can also review the configuration file
to provide all config.ini values as environment variables instead.
The above example shows how this is set up in an environment where the
certificate was generated using Let's Encrypt's ACME utility. Your paths
may differ. For Docker installations, ensure these paths are within a volume
or another directory accessible by the Docker container, such as /home/node/trilium-data/[DIR IN DATA DIRECTORY].
After configuring config.ini, restart Trilium and access the
hostname using "https".
If you opt to use a self-signed certificate for your server instance, note that the desktop instance will not trust it by default.
To bypass this, disable certificate validation by setting the following environment variable (for Linux):
export NODE_TLS_REJECT_UNAUTHORIZED=0
trilium
Trilium provides scripts to start in this mode, such as trilium-no-cert-check.bat for
Windows.
Warning: Disabling TLS certificate validation is insecure. Proceed only if you fully understand the implications.